ci: align release smoke controller lifecycle - #123
Merged
Conversation
![openswebot[bot]](https://avatars.githubusercontent.com/in/4340220?s=60&v=4){kind=small}
Owner
Author
|
Final verification on
The Open SWE GitHub check conclusion remained red despite that resolved dashboard state. Per the existing release decision, this upstream reconciliation mismatch is non-blocking; no review finding is being overridden. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Corrects the release-smoke fixture exposed by the published v2.2.1 canary. The product correctly fails a running migration when its controller is already archived; the fixture incorrectly created that controller archived. It also expected the synthetic home label after uninstall instead of the canonical
ThreadBeartitle required by the product contract.Manual smoke dispatches now execute the selected harness revision while the
taginput selects only the immutable public release assets. Tag-triggered reusable release calls continue to execute in their caller tag context.No product code, installer, or released asset changes.
Verification
scripts/release-smoke.sh v2.2.1passes against the public v2.2.1 manifest, checksums, binaries, and install command.go test ./... -count=1go test -race ./... -count=1go vet ./...sh -n scripts/release-smoke.shgit diff --checkNo findings.The published v2.2.1 tag remains immutable; the original red smoke run is retained as an honest historical record.